feat: add registry store for tracking agent registrations#104
Merged
jithinkunjachan merged 3 commits intomainfrom Apr 13, 2026
Merged
feat: add registry store for tracking agent registrations#104jithinkunjachan merged 3 commits intomainfrom
jithinkunjachan merged 3 commits intomainfrom
Conversation
Introduce a PostgreSQL-backed registry store that records agent instances and their heartbeat status during registration. The agent API now requires an X-Agent-Id header and upserts registry entries on each registration request. # Conflicts: # pkg/api/agents/client.go
jithinkunjachan
force-pushed
the
feat/add-registraion-store
branch
from
1ec3e72 to
404b8b6
Compare
push-tags-from-workflow
bot
added
dependencies
apatsap
requested changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce a PostgreSQL-backed registry store that records agent instances and their heartbeat status during registration.
The agent API now requires an X-Agent-Id header and upserts registry entries on each registration request.